- 
                Notifications
    You must be signed in to change notification settings 
- Fork 252
[Markdown] Contributing: Add section about release branch PRs #688
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| cc @shahmishal. | 
        
          
                contributing/_contributing-code.md
              
                Outdated
          
        
      |  | ||
| ### Release Branch Pull Requests | ||
|  | ||
| *All changes* to a release branch (`release/x.y`) must be nominated through pull | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's a nomination in this instance? Does it mean that you have to suggest your code for inclusion in a different forum before a PR can be opened or would
| *All changes* to a release branch (`release/x.y`) must be nominated through pull | |
| *All changes* to a release branch (`release/x.y`) must be done through pull | 
Be a better description
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nominated in the sense of proposed, but I’m happy to use "done" if you think it’s more apt. Let me have another go at rewording this to be crystal clear.
08f057b    to
    7717960      
    Compare
  
    7717960    to
    4884102      
    Compare
  
            
          
                contributing/_contributing-code.md
              
                Outdated
          
        
      | - **Reviewers**: The code owners that approved the mainline branch pull | ||
| requests. If any part of the mainline branch changes was not approved by a | ||
| respective code owner, provide a reason. Technical review can be delegated | ||
| by a code owner or otherwise requested as deemed appropriate or useful. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Second sentence amended per swiftlang/swift#72722 (comment). I would really like to add some clarity to that last sentence too, but that can wait.
4884102    to
    063d7d7      
    Compare
  
    b7c3c4f    to
    62421ad      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, only single suggestion.
62421ad    to
    43a80d1      
    Compare
  
    | Small change of plans: the form now lives in swiftlang/.github as a pull request template, so no need to inline it here. | 
43a80d1    to
    e22d942      
    Compare
  
    293efe1    to
    a63b862      
    Compare
  
    | Friendly ping, fellows. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
In an effort to centralize information about the release process, including guidance on formatting a release branch pull request, dedicate a section to this for repositories and forum announcements to refer to.
a63b862    to
    0b8db2c      
    Compare
  
    | @swift-ci test | 
| @0xTim Could we get an approval too to unblock merging? Thanks. 🙂 | 
Motivation:
In an effort to centralize information about the release process, including guidance on formatting a release branch pull request, dedicate a section to this for repositories and forum announcements to refer to.
Modifications:
—
Result:
—